Skip to content

[v1.16] chore(docs): update RELEASE_POLICY with v1.16.1#5992

Open
not4s wants to merge 1 commit into
firecracker-microvm:firecracker-v1.16from
not4s:chore/release-policy-v1.16.1
Open

[v1.16] chore(docs): update RELEASE_POLICY with v1.16.1#5992
not4s wants to merge 1 commit into
firecracker-microvm:firecracker-v1.16from
not4s:chore/release-policy-v1.16.1

Conversation

@not4s

@not4s not4s commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Changes

Bumping the v1.16 entry to v1.16.1 in the release status table, in preparation for the v1.16.1 patch release.

Reason

...

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkbuild --all to verify that the PR passes
    build checks on all supported architectures.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

@not4s not4s changed the title [v1.16] chore: update RELEASE_POLICY with v1.16.1 [v1.16] chore(docs): update RELEASE_POLICY with v1.16.1 Jun 23, 2026
Bump the v1.16 'Latest Patch' entry to v1.16.1 for the patch release.

Signed-off-by: Jay Chung <jaehoc@amazon.com>
@not4s not4s force-pushed the chore/release-policy-v1.16.1 branch from b2f303c to ac8db2c Compare June 23, 2026 16:21
@not4s not4s marked this pull request as ready for review June 23, 2026 16:31
@not4s not4s requested review from Manciukic and micz010 as code owners June 23, 2026 16:31
@not4s not4s added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Status: Awaiting review Indicates that a pull request is ready to be reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant